1 link tagged with all of: proof engineering + formal verification + ai + verification
Click any tag below to further narrow down your results
Links
The author argues that AI has pushed formal verification into the mainstream, but "formally verified" is a misleading label because proofs only cover what's specified, and the trusted base (definitions, models, provers) is still hard to check. He's optimistic about proving specific properties of software, especially single-threaded code, and thinks random testing will help validate the models used.
- Formal verification is now economically valuable and widely discussed, with AI generating large volumes of proofs, but that volume makes it more important to scrutinize what is actually trusted.
- Testing produces reviewable bug reports, while proofs rely on hard-to-verify components like specifications, machine models, and provers, so "formally verified" should always come with caveats about what's proven and what's assumed.
- Software with user-facing, "bouba" layers resists uniform correctness proofs, but specific properties of single-threaded programs are likely provable within years, with random testing helping to validate the models.